Repository navigation
Document botstopper_utm_referer_enabled setting - #536
Merged
Merged
Conversation
Contributor
tdgroot
approved these changes
Nov 10, 2026
This branch was previously deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Documents the new
botstopper_utm_referer_enabledsetting (hypernode-api!5881, hypernode-control!10672), which is enabled by default.When a visitor passes a Botstopper challenge, Botstopper appends the original external referer host to the post-challenge redirect URL as
utm_sourceandutm_medium=referralquery parameters, keeping referrer attribution working in client-side analytics tools such as Plausible and GA4.Changes
hypernode-systemctl settings botstopper_utm_referer_enabled.botstopper_utm_referer_enabledto the settings table and the Botstopper options list.